x86/layout: Correct Xen's idea of its own memory layout
authorAndrew Cooper <andrew.cooper3@citrix.com>
Tue, 14 Mar 2017 11:41:21 +0000 (12:41 +0100)
committerJan Beulich <jbeulich@suse.com>
Tue, 14 Mar 2017 11:41:21 +0000 (12:41 +0100)
commit8c2da8f4649bf5e29b6f3338132e36369e8f5700
tree5ef93c008b8a49ce0a870a8d27eacce63e6a5a27
parent6289c3b7c4756bca341ba59e4e246706040f7919
x86/layout: Correct Xen's idea of its own memory layout

c/s b4cd59fe "x86: reorder .data and .init when linking" had an unintended
side effect, where xen_in_range() and the tboot S3 MAC were no longer correct.

In practice, it means that Xen's .data section is excluded from consideration,
which means:
 1) Default IOMMU construction for the hardware domain could create mappings.
 2) .data isn't included in the tboot MAC checked on resume from S3.

Adjust the comments and virtual address anchors used to define the regions.

Reported-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
master commit: c9a4a1c419cebac83a8fb60c4532ad8ccc973dc4
master date: 2017-02-28 16:18:38 +0000
xen/arch/x86/setup.c
xen/arch/x86/tboot.c